Changing the from address in sharing email in SharePoint 2016

Question

In SharePoint 2016, When we share a document with other users, SharePoint send the sharing email to the users with the link of the item. In that email, from address is the user's own address ( which shared the document) and to address is end user's address.

But when we setup alerts in SharePoint, it send the email using the email address which we set in the outgoing email settings.

Now problem is, Alert email pass through our exchange relay but sharing emails blocked due to company policy.

Is there any workaround which force SharePoint to send the email always using the generic email address not user's own email address. Any powershell script or SMTP related configuration on SharePoint side only.

Answer 1

It can't be done. This behavior is hard coded. Your only option is to adjust the parameters of an Exchange Receive Connector (or what ever mail server you're using) to accept these emails, or create a new RC to accept these emails.

Answer 2

Finally this issue resolved in SharePoint 2016 Novemebr 2017 CU.

Some SharePoint features impersonate end users when sending email to personalize the message. For example, when a user requests access to a site, SharePoint will set the "From" address of the email notification as the user who made the request.

Some SMTP servers may block impersonation to protect users from unauthorized attempts to spoof their identities. If your SMTP server blocks impersonation, you can now configure each SharePoint web application to disable this behavior. This will ensure that SharePoint always uses the "From" address that is specified at the web application level.

Follow these steps to disable SharePoint email impersonation:

1. Launch the SharePoint 2016 Management Shell.

2. Run the following commands:

   $webapp = Get-SPWebApplication

   $webapp.OutboundMailOverrideEnvelopeSender = $true

   $webapp.Update()

Description of the security update for SharePoint Server 2016: November 14, 2017

You can read more about this: https://blogs.msdn.microsoft.com/joerg_sinemus/2017/11/15/sharepoint-2016-november-2017-cu/