Reason: [{LED=250 2.1.5 RESOLVER.GRP.BlockedMessage; messages of this type are not delivered to groups};{MSG=};{FQDN=};{IP=};{LRT=}]

Question

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. External automatic replies are being delivered to the distribution list with no issues. This doesn't seem to be caused by a transport rule. We're running a hybrid setup and this distribution list was created on premise. I have also set the reportToOriginator attribute to true. Would anyone be able to assist?

Answer 1

To address the issue of automatic reply messages failing to be delivered to a distribution list with the "RESOLVER.GRP.BlockedMessage" error, follow these technical resolution steps:

• Review Error Details**: Analyze the error message to understand the specific reason for the message blockage. In this case, the error code "250 2.1.5 RESOLVER.GRP.BlockedMessage" indicates that messages of this type are not delivered to groups.
• Check Distribution List Configuration**: Verify the configuration settings of the distribution list to ensure that it is correctly configured to accept automatic reply messages. Check for any restrictions or limitations that may be preventing automatic replies from being delivered to the list.
• Verify Transport Rules**: Although it's mentioned that the issue doesn't seem to be caused by a transport rule, double-check the existing transport rules to confirm that none of them are inadvertently blocking automatic reply messages to the distribution list. Ensure that there are no conflicting rules affecting message delivery.
• Hybrid Setup Consideration**: Since you are running a hybrid setup, consider any configuration differences or limitations between on-premise and cloud-based distribution lists. Ensure that the distribution list properties are correctly synchronized between the on-premise and cloud environments.
• Review Automatic Reply Settings**: Check the automatic reply settings for the user attempting to send the message to the distribution list. Ensure that automatic replies are enabled and configured correctly for internal recipients, including distribution lists.
• Investigate ReportToOriginator Attribute**: Although the reportToOriginator attribute has been set to true, verify that it is applied correctly and functioning as expected. Ensure that it is configured at the appropriate level (e.g., user mailbox, distribution list).
• Test with Different Scenarios**: Conduct tests with different scenarios, such as sending automatic replies from different users to the distribution list, to identify if the issue is specific to certain users or message types.
• Consult Microsoft Support**: If the issue persists despite troubleshooting efforts, consider reaching out to Microsoft Support for further assistance. Provide them with detailed information about your hybrid setup, distribution list configuration, and the steps you've taken to troubleshoot the issue.
• Monitor for Changes**: After implementing any changes or adjustments, monitor the email flow and message delivery to ensure that automatic reply messages are successfully delivered to the distribution list without encountering the "RESOLVER.GRP.BlockedMessage" error.

By following these technical resolution steps, you can diagnose and address the issue preventing automatic reply messages from being delivered to the distribution list in your hybrid environment.