We made the change to start using Exchange Web Services to send messages for user-generated actions from SharePoint Online. For example, before this change a user named Alice, who doesn't have an Exchange Online mailbox shares a file in SharePoint Online with Bob. Because Alice doesn't have an Exchange Online mailbox, we would send the message from the SharePoint Online Simple Mail Transfer Protocol (SMTP) servers, and then spoof the From field of the message to have the name and email address of Alice. If the spoofed message has conflicts with spam filters, the message is delivered to the Junk Email folder or rejected completely. In the past, we advised you to include the SPF records for "sharepointonline.com" in your SPF records as a mitigation for this problem. The change to SharePoint Online will no longer spoof the email address for such messages. These messages will have the same display name (such as the person who is doing the sharing), but will always use firstname.lastname@example.org as the From address.
Customers will no longer have to change their own SPF records or add rules to their spam filters to enable the delivery of notification messages from SharePoint Online. Additionally, messages that are generated by user initiated-actions in which the user has an Exchange Online mailbox will continue to be sent from the user's mailbox and are not subject to being flagged as junk email.
Because of this change, SharePoint Online will no longer honor the setting Email Notifications for newsfeed notifications that is found in the SharePoint Admin Center. The notification email messages from newsfeeds will always use the email@example.com as the From address. This setting will be removed in a future release.
The features that are affected by this change include the following:
- Message sharing if the user does not have an Exchange Online mailbox
- Access Requests if the user does not have an Exchange Online mailbox
- SharePoint Newsfeed notification messages
- Custom messages that are generated by workflows if the From address was changed to a different address
Article ID: 3134824 - Last Review: Mar 31, 2017 - Revision: 1