Article ID: 2618599 - View products that this article applies to.
Consider the following scenario in Microsoft Office 365 dedicated:
In this scenario, some members of the distribution group may not receive the email message. Additionally, you do not receive a non-delivery report (NDR).
This issue occurs because some email servers do not accept email messages that do not specify a return path. This behavior is a method of spam prevention. For example, consider the following example Simple Mail Transfer Protocol (SMTP) conversation:
Server: 220 smtp.contoso.com ESMTP Postfix
Client: HELLO relay.example.org
Server: 250 Hello relay.example.org, I am glad to meet you
Client: MAIL FROM: <>
Server: 250 Ok
Client: RCPT TO: firstname.lastname@example.org
In this example, the recipient server rejects the email message because the message does not have a return path.
Most frequently, the email message does not have a return path if both the ReportToManager and ReportToOriginator distribution group attributes are set to False, as follows:
To resolve this issue, set the Return-Path value to one of the following values:
To make this setting, use one of the following methods to set the attributes on the managed object by using Windows PowerShell cmdlets.
Method 1: Set the Return-Path value to the owner of the distribution group regardless of the senderTo set the Return-Path value to the owner of the distribution group, set the value of the ReportToManagerEnabled attribute to True by using the following cmdlet:
Set-DistributionGroup email@example.com –ReportToManagerEnabled $TRUE
Method 2: Set the Return-Path value to the sender of the messageTo set the Return-Path value to the sender, set the value of the ReportToOriginatorEnabled attribute to True by using the following cmdlet:
Note Both attributes that are mentioned in these methods are Microsoft Managed Services Service Provisioning Provider (MMSSPP) direct flow attributes. Therefore, any modifications that are made to these attributes in the managed environment are overwritten during the next MMSSPP synchronization. Any permanent modifications to these attributes must be made in the customer's Active Directory Domain Services, and these modifications must be able to synchronize through MMSSPP.
Set-DistributionGroup firstname.lastname@example.org –ReportToOriginatorEnabled $TRUE
These attributes are displayed in Active Directory Domain Services as follows:
Article ID: 2618599 - Last Review: January 24, 2013 - Revision: 6.0